Multiple household management

ABSTRACT

Embodiments described herein include systems and methods for providing a management interface for controlling multiple households. The management interface may be provided as an application on a mobile device or as an Internet webpage. An example implementation involves a device displaying representations of: a plurality of households; an indication of a selected household; one or more zones within the selected household; and a representation of media being played by a selected zone of the one or more zones. While displaying the representations, the device receives, from a server, data indicating updated information associated with the plurality of households; and, in response, updates the graphical display to display at least an updated representation of media being played by the selected zone.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority under 35 U.S.C. § 120 to, and is a continuation of, U.S. non-provisional patent application Ser. No. 16/458,453, filed on Jul. 1, 2019, entitled “Multiple Household Management,” which is incorporated herein by reference in its entirety.

U.S. non-provisional patent application Ser. No. 16/458,453 claims priority under 35 U.S.C. § 120 to, and is a continuation of, U.S. non-provisional patent application Ser. No. 16/143,301, filed on Sep. 26, 2018, entitled “Multiple Household Management Interface,” and issued as U.S. Pat. No. 10,341,736 on Jul. 2, 2019, which is incorporated herein by reference in its entirety.

U.S. non-provisional patent application Ser. No. 16/143,301 claims priority under 35 U.S.C. § 120 to, and is a continuation of, U.S. non-provisional patent application Ser. No. 15/227,074, filed on Aug. 3, 2016, entitled “Media Experience Social Interface,” and issued as U.S. Pat. No. 10,097,893 on Oct. 9, 2018, which is incorporated herein by reference in its entirety.

U.S. non-provisional patent application Ser. No. 15/227,074 claims priority under 35 U.S.C. § 120 to, and is a continuation of, U.S. non-provisional patent application Ser. No. 13/748,357, filed on Jan. 23, 2013, entitled “System and Method for a Media Experience Social Interface,” issued as U.S. Pat. No. 9,510,055 on Nov. 29, 2016, which is incorporated herein by reference in its entirety.

FIELD OF THE DISCLOSURE

The disclosure is related to consumer goods and, more particularly, to systems, products, features, services, and other items directed to media playback or some aspect thereof.

BACKGROUND

Technological advancements have increased the accessibility of music content, as well as other types of media, such as television content, movies, and interactive content. For example, a user can access audio, video, or both audio and video content over the Internet through an online store, an Internet radio station, a music service, a movie service, and so on, in addition to the more traditional avenues of accessing audio and video content. Demand for audio, video, and both audio and video content inside and outside of the home continues to increase.

BRIEF DESCRIPTION OF THE DRAWINGS

Features, aspects, and advantages of the presently disclosed technology may be better understood with regard to the following description, appended claims, and accompanying drawings where:

FIG. 1 shows an example configuration in which certain embodiments may be practiced;

FIG. 2A shows an illustration of an example zone player having a built-in amplifier and transducers;

FIG. 2B shows an illustration of an example zone player having a built-in amplifier and connected to external speakers;

FIG. 2C shows an illustration of an example zone player connected to an A/V receiver and speakers;

FIG. 3 shows an illustration of an example controller;

FIG. 4 shows an internal functional block diagram of an example zone player;

FIG. 5 shows an internal functional block diagram of an example controller;

FIG. 6 shows an example ad-hoc playback network;

FIG. 7 shows a system of a plurality of networks including a cloud-based network and at least one local playback network;

FIG. 8 shows an example system configuration between a media experience social interface and zone player households;

FIG. 9A shows an example flow diagram for updating a media experience social interface;

FIG. 9B shows an example flow diagram for providing a media experience social interface;

FIG. 10A shows an example first media experience social interface;

FIG. 10B shows an example second media experience social interface; and

FIG. 11 shows an example interface for modifying a media experience sharing configuration.

In addition, the drawings are for the purpose of illustrating example embodiments, but it is understood that the inventions are not limited to the arrangements and instrumentality shown in the drawings.

DETAILED DESCRIPTION I. Overview

Embodiments described herein include systems and methods, among numerous other inventions, for providing a social interface for sharing media experience information between a community of households. In the following description, a household may refer to any particular location having a media system through which people at the location may experience media. By way of illustration, a location might include a residential unit, a commercial or retail business, an office, a hotel, a boat, a vehicle, an outside location such as a park, and so on. A group of different households (e.g., households of family, friends, and/or acquaintances) may form a community. In this case, the system of each household in the community may share information with one another, via the Internet, for example. In some embodiments, the system of each household in the community communicates with one another. In other embodiments, the system of each household in the community communicates with a central server or database. In one example, the social interface may display a list of households in the community, and a user of the social interface may then select a household from the list to, among other actions, view information on media being experienced within a particular household in the community.

In some cases, a particular household in the community may include separate groups (or zones) of media players configured to render media in synchrony. As such, the social interface may display, upon selection of the particular household, a list of the groups of media players included in the selected household. In this case, the user may then select a group from the list of groups to view information on media being rendered by the media players in the selected group. In addition to information on media being rendered by the selected group, the social interface may also provide information on other media accessible by the selected group, such as a playlist or music library associated with the selected group.

In some cases, if a user is interested in the media being experienced at another household in the community, the user may retrieve a copy of the information to view locally. For instance, if a person at the community household is enjoying a music playlist of interest to the user, the user's own household system may retrieve a copy of the playlist. In one instance, the copy of the playlist may strictly be a listing of media, and may not necessarily include access to media in the playlist.

In another case, the user may also choose to experience locally the same media being experienced by another household in the community. For instance, if the user retrieved a copy of the music playlist enjoyed by a friend in the friend's household, the user may play locally in the user's household, from the music playlist, media the user has access rights to. The user may access the media from the user's account of the same service used by the friend, a different media service, or via a local library of media. Metadata or another form of identification may be used to identify and locate the media for play back.

In yet another case, the user may choose to experience locally the same media being experienced in another household by selecting a zone or zone group of the other household to play the same media. As such, a player or group of players in the local household may be directed over the Internet to a player or group of players in the other household to retrieve and play the media. In one example, the user may experience the media via the access rights of the other household. For instance, a player in the local household may be given a URL that addresses an appropriate device or player in the other household. In another example, the user may experience the media via the access rights of the user in cases where the access rights of the user enable the user to obtain the same or substantially similar media as the other household.

In a further case, the user may control the media experienced by another household of the community. In some embodiments this calls for the other household to have given control access to the user. For instance, a friend may ask the user to introduce him/her to new music, and may provide control access rights to the user. In this instance, the user may, via the user's social interface, browse music accessible by the friend and pick out music to be rendered in the friend's household for the friend to experience. In another instance, the friend may ask the user to put together or “DJ” a playlist of songs for a gathering later in the friend's household. In this instance, the friend may provide control access rights to the user, and the user may, via the social interface, generate a playlist from media accessible by the friend, to be rendered in the friend's household.

In one example, the social interface discussed above may be provided to the user on a personal device of the user. The personal device may be a mobile media player such as an APPLE IPOD®, or a smart phone such as an APPLE IPHONE® or any ANDROID™ powered phone that may be configured to be in communication with the media systems and households in the community. In this example, the social interface may be in the form of a software application on the personal device. In another example, the social interface may be provided on a controller of one or more media systems in a household. In this example, the controller may also be in the form of an application on the personal device. In some cases, the social interface may be included with the controller application.

In yet another example, the social interface may be provided on a website on the World Wide Web accessible over the Internet, or via a “cloud” computing service. In this example, the user may log on to a website (via a web browser on a computer or web browsing application on a personal device) to access the social interface to view information on media experiences, retrieve the media experience information, and/or control the media experiences of the friend.

As discussed above, systems and methods, among other inventions, for sharing media experience information among households are provided herein. In particular, a social interface for displaying the media experience information is discussed. In one aspect, a method for displaying media information for a household of a community of households on a display screen is provided. The method involves displaying on a display screen a representation of a zone player group associated with a household responsive to receipt of a command to select the household from a community of households, and displaying on the display screen a representation of media being rendered by the zone player group, wherein the representation of the media indicates information associated with the media being rendered.

In another aspect, a non-transitory computer readable medium is provided. The non-transitory computer readable medium has stored thereon instructions executable by a computing device to cause the computing device to perform functions. The functions include displaying on a display screen a representation of a zone player group associated with a household responsive to receipt of a command to select the household from a community of households, and displaying on the display screen a representation of media being rendered by the zone player group, wherein the representation of the media indicates information associated with the media being rendered.

II. Example Operating Environment

Referring now to the drawings, in which like numerals can refer to like parts throughout the figures, FIG. 1 shows an example media system configuration 100 in which one or more embodiments disclosed herein can be practiced or implemented.

By way of illustration, the media system configuration 100 represents a home (or household, as mentioned above) with multiple zones (or groups, as mentioned above), though the household could have been configured with only one zone. Each zone, for example, may represent a different room or space, such as an office, bathroom, bedroom, kitchen, dining room, family room, home theater room, utility or laundry room, and patio. A single zone might also include multiple rooms or spaces if so configured. One or more of zone players 102-124 are shown in each respective zone. A zone player 102-124, also referred to as a playback device, multimedia unit, speaker, player, and so on, provides audio, video, and/or audiovisual output. A controller 130 (e.g., shown in the kitchen for purposes of illustration) provides control to the media system configuration 100. Controller 130 may be fixed to a zone, or alternatively, mobile such that it can be moved about the zones. The media system configuration 100 may also include more than one controller 130. The media system configuration 100 illustrates an example whole house media system, though it is understood that the technology described herein is not limited to its particular place of application or to an expansive system like a whole house media system 100 of FIG. 1.

a. Example Zone Players

FIGS. 2A, 2B, and 2C show example types of zone players. Zone players 200, 202, and 204 of FIGS. 2A, 2B, and 2C, respectively, can correspond to any of the zone players 102-124 of FIG. 1, for example. In some embodiments, audio is reproduced using only a single zone player, such as by a full-range player. In some embodiments, audio is reproduced using two or more zone players, such as by using a combination of full-range players or a combination of full-range and specialized players. In some embodiments, zone players 200-204 may also be referred to as a “smart speaker,” because they contain processing capabilities beyond the reproduction of audio, more of which is described below.

FIG. 2A illustrates zone player 200 that includes sound producing equipment 208 capable of reproducing full-range sound. The sound may come from an audio signal that is received and processed by zone player 200 over a wired or wireless data network. Sound producing equipment 208 includes one or more built-in amplifiers and one or more acoustic transducers (e.g., speakers). A built-in amplifier is described more below with respect to FIG. 4. A speaker or acoustic transducer can include, for example, any of a tweeter, a mid-range driver, a low-range driver, and a subwoofer. In some embodiments, zone player 200 can be statically or dynamically configured to play stereophonic audio, monaural audio, or both. In some embodiments, zone player 200 is configured to reproduce a subset of full-range sound, such as when zone player 200 is grouped with other zone players to play stereophonic audio, monaural audio, and/or surround audio or when the audio content received by zone player 200 is less than full-range.

FIG. 2B illustrates zone player 202 that includes a built-in amplifier to power a set of detached speakers 210. A detached speaker can include, for example, any type of loudspeaker. Zone player 202 may be configured to power one, two, or more separate loudspeakers. Zone player 202 may be configured to communicate an audio signal (e.g., right and left channel audio or more channels depending on its configuration) to the detached speakers 210 via a wired path.

FIG. 2C illustrates zone player 204 that does not include a built-in amplifier, but is configured to communicate an audio signal, received over a data network, to an audio (or “audio/video”) receiver 214 with built-in amplification.

Referring back to FIG. 1, in some embodiments, one, some, or all of the zone players 102 to 124 can retrieve audio directly from a source. For example, a zone player may contain a playlist or queue of audio items to be played (also referred to herein as a “playback queue”). Each item in the queue may comprise a uniform resource identifier (URI) or some other identifier. The URI or identifier can point the zone player to the audio source. The source might be found on the Internet (e.g., the cloud), locally from another device over data network 128 (described further below), from the controller 130, stored on the zone player itself, or from an audio source communicating directly to the zone player. In some embodiments, the zone player can reproduce the audio itself, send it to another zone player for reproduction, or both where the audio is played by the zone player and one or more additional zone players in synchrony. In some embodiments, the zone player can play a first audio content (or not play at all), while sending a second, different audio content to another zone player(s) for reproduction.

By way of illustration, SONOS, Inc. of Santa Barbara, Calif. presently offers for sale zone players referred to as a “PLAY:5,” “PLAY:3,” “CONNECT:AMP,” “CONNECT,” and “SUB.” Any other past, present, and/or future zone players can additionally or alternatively be used to implement the zone players of example embodiments disclosed herein. Additionally, it is understood that a zone player is not limited to the particular examples illustrated in FIGS. 2A, 2B, and 2C or to the SONOS product offerings. For example, a zone player may include a wired or wireless headphone. In yet another example, a zone player might include a sound bar for television. In yet another example, a zone player can include or interact with a docking station for an Apple IPOD™ or similar device.

b. Example Controllers

FIG. 3 illustrates an example wireless controller 300 in docking station 302. By way of illustration, controller 300 may correspond to controlling device 130 of FIG. 1. Docking station 302, if provided, may be used to charge a battery of controller 300. In some embodiments, controller 300 may be provided with a touch screen 304 that allows a user to interact through touch with the controller 300, for example, to retrieve and navigate a playlist of audio items, control operations of one or more zone players, and provide overall control of the system configuration 100. In certain embodiments, any number of controllers can be used to control the system configuration 100. In some embodiments, there may be a limit set on the number of controllers that can control the system configuration 100. The controllers might be wireless like wireless controller 300 or wired to data network 128.

In some embodiments, if more than one controller is used in system 100, each controller may be coordinated to display common content, and may all be dynamically updated to indicate changes made from a single controller. Coordination can occur, for instance, by a controller periodically requesting a state variable directly or indirectly from one or more zone players; the state variable may provide information about system 100, such as current zone group configuration, what is playing in one or more zones, volume levels, and other items of interest. The state variable may be passed around on data network 128 between zone players (and controllers, if so desired) as needed or as often as programmed.

In addition, an application running on any network-enabled portable device, such as an IPHONE™, IPAD™, ANDROID™ powered phone, or any other smart phone or network-enabled device can be used as controller 130. An application running on a laptop or desktop personal computer (PC) or Mac™ can also be used as controller 130. Such controllers may connect to system 100 through an interface with data network 128, a zone player, a wireless router, or using some other configured connection path. Example controllers offered by Sonos, Inc. of Santa Barbara, Calif. include a “Controller 200,” “SONOS® CONTROL,” “SONOS® Controller for IPHONE™,” “SONOS® Controller for IPAD™,” “SONOS® Controller for ANDROID™,” “SONOS® Controller for MAC™ or PC.”

c. Example Data Connection

Zone players 102 to 124 of FIG. 1 are coupled directly or indirectly to a data network, such as data network 128. Controller 130 may also be coupled directly or indirectly to data network 128 or individual zone players. Data network 128 is represented by an octagon in the figure to stand out from other representative components. While data network 128 is shown in a single location, it is understood that such a network is distributed in and around system 100. Particularly, data network 128 can be a wired network, a wireless network, or a combination of both wired and wireless networks. In some embodiments, one or more of the zone players 102-124 are wirelessly coupled to data network 128 based on a proprietary mesh network. In some embodiments, one or more of the zone players 102-124 are wirelessly coupled to data network 128 using a non-mesh topology. In some embodiments, one or more of the zone players 102-124 are coupled via a wire to data network 128 using Ethernet or similar technology. In addition to the one or more zone players 102-124 connecting to data network 128, data network 128 can further allow access to a wide area network, such as the Internet.

In some embodiments, connecting any of the zone players 102-124, or some other connecting device, to a broadband router, can create data network 128. Other zone players 102-124 can then be added wired or wirelessly to the data network 128. For example, a zone player (e.g., any of zone players 102-124) can be added to the system configuration 100 by simply pressing a button on the zone player itself (or perform some other action), which enables a connection to be made to data network 128. The broadband router can be connected to an Internet Service Provider (ISP), for example. The broadband router can be used to form another data network within the system configuration 100, which can be used in other applications (e.g., web surfing). Data network 128 can also be used in other applications, if so programmed. An example, second network may implement SONOSNET™ protocol, developed by SONOS, Inc. of Santa Barbara. SONOSNET™ represents a secure, AES-encrypted, peer-to-peer wireless mesh network. Alternatively, in certain embodiments, the data network 128 is the same network, such as a traditional wired or wireless network, used for other applications in the household.

d. Example Zone Configurations

A particular zone can contain one or more zone players. For example, the family room of FIG. 1 contains two zone players 106 and 108, while the kitchen is shown with one zone player 102. In another example, the home theater room contains additional zone players to play audio from a 5.1 channel or greater audio source (e.g., a movie encoded with 5.1 or greater audio channels). In some embodiments, one can position a zone player in a room or space and assign the zone player to a new or existing zone via controller 130. As such, zones may be created, combined with another zone, removed, and given a specific name (e.g., “Kitchen”), if so desired and programmed to do so with controller 130. Moreover, in some embodiments, zone configurations may be dynamically changed even after being configured using controller 130 or some other mechanism.

In some embodiments, if a zone contains two or more zone players, such as the two zone players 106 and 108 in the family room, then the two zone players 106 and 108 can be configured to play the same audio source in synchrony, or the two zone players 106 and 108 can be paired to play two separate sounds in left and right channels, for example. In other words, the stereo effects of a sound can be reproduced or enhanced through the two zone players 106 and 108, one for the left sound and the other for the right sound. In certain embodiments, paired zone players (also referred to as “bonded zone players”) can play audio in synchrony with other zone players in the same or different zones.

In some embodiments, two or more zone players can be sonically consolidated to form a single, consolidated zone player. A consolidated zone player (though made up of multiple, separate devices) can be configured to process and reproduce sound differently than an unconsolidated zone player or zone players that are paired, because a consolidated zone player will have additional speaker drivers from which sound can be passed. The consolidated zone player can further be paired with a single zone player or yet another consolidated zone player. Each playback device of a consolidated playback device can be set in a consolidated mode, for example.

According to some embodiments, one can continue to do any of: group, consolidate, and pair zone players, for example, until a desired configuration is complete. The actions of grouping, consolidation, and pairing are preferably performed through a control interface, such as using controller 130, and not by physically connecting and re-connecting speaker wire, for example, to individual, discrete speakers to create different configurations. As such, certain embodiments described herein provide a more flexible and dynamic platform through which sound reproduction can be offered to the end-user.

e. Example Audio Sources

In some embodiments, each zone can play from the same audio source as another zone or each zone can play from a different audio source. For example, someone can be grilling on the patio and listening to jazz music via zone player 124, while someone is preparing food in the kitchen and listening to classical music via zone player 102. Further, someone can be in the office listening to the same jazz music via zone player 110 that is playing on the patio via zone player 124. In some embodiments, the jazz music played via zone players 110 and 124 is played in synchrony. Synchronizing playback amongst zones allows for someone to pass through zones while seamlessly (or substantially seamlessly) listening to the audio. Further, zones can be put into a “party mode” such that all associated zones will play audio in synchrony.

Sources of audio content to be played by zone players 102-124 are numerous. In some embodiments, music on a zone player itself may be accessed and a played. In some embodiments, music from a personal library stored on a computer or networked-attached storage (NAS) may be accessed via the data network 128 and played. In some embodiments, Internet radio stations, shows, and podcasts can be accessed via the data network 128. Music or cloud services that let a user stream and/or download music and audio content can be accessed via the data network 128. Further, music can be obtained from traditional sources, such as a turntable or CD player, via a line-in connection to a zone player, for example. Audio content can also be accessed using a different protocol, such as AIRPLAY™, which is a wireless technology by Apple, Inc., for example. Audio content received from one or more sources can be shared amongst the zone players 102 to 124 via data network 128 and/or controller 130. The above-disclosed sources of audio content are referred to herein as network-based audio information sources. However, network-based audio information sources are not limited thereto.

In some embodiments, the example home theater zone players 116, 118, 120 are coupled to an audio information source such as a television 132. In some examples, the television 132 is used as a source of audio for the home theater zone players 116, 118, 120, while in other examples audio information from the television 132 can be shared with any of the zone players 102-124 in the audio system 100.

III. Example Zone Players

Referring now to FIG. 4, there is shown an example block diagram of a zone player 400 in accordance with an embodiment. Zone player 400 includes a network interface 402, a processor 408, a memory 410, an audio processing component 412, one or more modules 414, an audio amplifier 416, and a speaker unit 418 coupled to the audio amplifier 416. FIG. 2A shows an example illustration of such a zone player. Other types of zone players may not include the speaker unit 418 (e.g., such as shown in FIG. 2B) or the audio amplifier 416 (e.g., such as shown in FIG. 2C). Further, it is contemplated that the zone player 400 can be integrated into another component. For example, the zone player 400 could be constructed as part of a television, lighting, or some other device for indoor or outdoor use.

In some embodiments, network interface 402 facilitates a data flow between zone player 400 and other devices on a data network 128. In some embodiments, in addition to getting audio from another zone player or device on data network 128, zone player 400 may access audio directly from the audio source, such as over a wide area network or on the local network. In some embodiments, the network interface 402 can further handle the address part of each packet so that it gets to the right destination or intercepts packets destined for the zone player 400. Accordingly, in certain embodiments, each of the packets includes an Internet Protocol (IP)-based source address as well as an IP-based destination address.

In some embodiments, network interface 402 can include one or both of a wireless interface 404 and a wired interface 406. The wireless interface 404, also referred to as a radio frequency (RF) interface, provides network interface functions for the zone player 400 to wirelessly communicate with other devices (e.g., other zone player(s), speaker(s), receiver(s), component(s) associated with the data network 128, and so on) in accordance with a communication protocol (e.g., any wireless standard including IEEE 802.11a, 802.11b, 802.11g, 802.11n, or 802.15). Wireless interface 404 may include one or more radios. To receive wireless signals and to provide the wireless signals to the wireless interface 404 and to transmit wireless signals, the zone player 400 includes one or more antennas 420. The wired interface 406 provides network interface functions for the zone player 400 to communicate over a wire with other devices in accordance with a communication protocol (e.g., IEEE 802.3). In some embodiments, a zone player includes multiple wireless 404 interfaces. In some embodiments, a zone player includes multiple wired 406 interfaces. In some embodiments, a zone player includes both of the interfaces 404 and 406. In some embodiments, a zone player 400 includes only the wireless interface 404 or the wired interface 406.

In some embodiments, the processor 408 is a clock-driven electronic device that is configured to process input data according to instructions stored in memory 410. The memory 410 is data storage that can be loaded with one or more software module(s) 414, which can be executed by the processor 408 to achieve certain tasks. In the illustrated embodiment, the memory 410 is a tangible machine-readable medium storing instructions that can be executed by the processor 408. In some embodiments, a task might be for the zone player 400 to retrieve audio data from another zone player or a device on a network (e.g., using a uniform resource locator (URL) or some other identifier). In some embodiments, a task may be for the zone player 400 to send audio data to another zone player or device on a network. In some embodiments, a task may be for the zone player 400 to synchronize playback of audio with one or more additional zone players. In some embodiments, a task may be to pair the zone player 400 with one or more zone players to create a multi-channel audio environment. Additional or alternative tasks can be achieved via the one or more software module(s) 414 and the processor 408.

The audio processing component 412 can include one or more digital-to-analog converters (DAC), an audio preprocessing component, an audio enhancement component or a digital signal processor, and so on. In some embodiments, the audio processing component 412 may be part of processor 408. In some embodiments, the audio that is retrieved via the network interface 402 is processed and/or intentionally altered by the audio processing component 412. Further, the audio processing component 412 can produce analog audio signals. The processed analog audio signals are then provided to the audio amplifier 416 for play back through speakers 418. In addition, the audio processing component 412 can include circuitry to process analog or digital signals as inputs to play from zone player 400, send to another zone player on a network, or both play and send to another zone player on the network. An example input includes a line-in connection (e.g., an auto-detecting 3.5 mm audio line-in connection).

The audio amplifier 416 is a device(s) that amplifies audio signals to a level for driving one or more speakers 418. The one or more speakers 418 can include an individual transducer (e.g., a “driver”) or a complete speaker system that includes an enclosure including one or more drivers. A particular driver can be a subwoofer (e.g., for low frequencies), a mid-range driver (e.g., for middle frequencies), and a tweeter (e.g., for high frequencies), for example. An enclosure can be sealed or ported, for example. Each transducer may be driven by its own individual amplifier.

A commercial example, presently known as the PLAY:5™, is a zone player with a built-in amplifier and speakers that is capable of retrieving audio directly from the source, such as on the Internet or on the local network, for example. In particular, the PLAY:5™ is a five-amp, five-driver speaker system that includes two tweeters, two mid-range drivers, and one woofer. When playing audio content via the PLAY:5, the left audio data of a track is sent out of the left tweeter and left mid-range driver, the right audio data of a track is sent out of the right tweeter and the right mid-range driver, and mono bass is sent out of the subwoofer. Further, both mid-range drivers and both tweeters have the same equalization (or substantially the same equalization). That is, they are both sent the same frequencies but from different channels of audio. Audio from Internet radio stations, online music and video services, downloaded music, analog audio inputs, television, DVD, and so on, can be played from the PLAY:5™.

IV. Example Controller

Referring now to FIG. 5, there is shown an example block diagram for controller 500, which can correspond to the controlling device 130 in FIG. 1. Controller 500 can be used to facilitate the control of multi-media applications, automation and others in a system. In particular, the controller 500 may be configured to facilitate a selection of a plurality of audio sources available on the network and enable control of one or more zone players (e.g., the zone players 102-124 in FIG. 1) through a wireless or wired network interface 508. According to one embodiment, the wireless communications is based on an industry standard (e.g., infrared, radio, wireless standards including IEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.15, and so on). Further, when a particular audio is being accessed via the controller 500 or being played via a zone player, a picture (e.g., album art) or any other data, associated with the audio and/or audio source can be transmitted from a zone player or other electronic device to controller 500 for display.

Controller 500 is provided with a screen 502 and an input interface 514 that allows a user to interact with the controller 500, for example, to navigate a playlist of many multimedia items and to control operations of one or more zone players. The screen 502 on the controller 500 can be an LCD screen, for example. The screen 500 communicates with and is commanded by a screen driver 504 that is controlled by a microcontroller (e.g., a processor) 506. The memory 510 can be loaded with one or more application modules 512 that can be executed by the microcontroller 506 with or without a user input via the user interface 514 to achieve certain tasks. In some embodiments, an application module 512 is configured to facilitate grouping a number of selected zone players into a zone group and synchronizing the zone players for audio play back. In some embodiments, an application module 512 is configured to control the audio sounds (e.g., volume) of the zone players in a zone group. In operation, when the microcontroller 506 executes one or more of the application modules 512, the screen driver 504 generates control signals to drive the screen 502 to display an application specific user interface accordingly.

The controller 500 includes a network interface 508 that facilitates wired or wireless communication with a zone player. In some embodiments, the commands such as volume control and audio playback synchronization are sent via the network interface 508. In some embodiments, a saved zone group configuration is transmitted between a zone player and a controller via the network interface 508. The controller 500 can control one or more zone players, such as 102-124 of FIG. 1. There can be more than one controller for a particular system, and each controller may share common information with another controller, or retrieve the common information from a zone player, if such a zone player stores configuration data (e.g., such as a state variable). Further, a controller can be integrated into a zone player.

It should be noted that other network-enabled devices such as an IPHONE™, IPAD™ or any other smart phone or network-enabled device (e.g., a networked computer such as a PC or MAC™) can also be used as a controller to interact or control zone players in a particular environment. In some embodiments, a software application or upgrade can be downloaded onto a network-enabled device to perform the functions described herein.

In certain embodiments, a user can create a zone group (also referred to as a bonded zone) including at least two zone players from the controller 500. The zone players in the zone group can play audio in a synchronized fashion, such that all of the zone players in the zone group play back an identical audio source or a list of identical audio sources in a synchronized manner such that no (or substantially no) audible delays or hiccups are to be heard. Similarly, in some embodiments, when a user increases the audio volume of the group from the controller 500, the signals or data of increasing the audio volume for the group are sent to one of the zone players and causes other zone players in the group to be increased together in volume.

A user via the controller 500 can group zone players into a zone group by activating a “Link Zones” or “Add Zone” soft button, or de-grouping a zone group by activating an “Unlink Zones” or “Drop Zone” button. For example, one mechanism for ‘joining’ zone players together for audio play back is to link a number of zone players together to form a group. To link a number of zone players together, a user can manually link each zone player or room one after the other. For example, assume that there is a multi-zone system that includes the following zones: Bathroom, Bedroom, Den, Dining Room, Family Room, and Foyer.

In certain embodiments, a user can link any number of the six zone players, for example, by starting with a single zone and then manually linking each zone to that zone.

In certain embodiments, a set of zones can be dynamically linked together using a command to create a zone scene or theme (subsequent to first creating the zone scene). For instance, a “Morning” zone scene command can link the Bedroom, Office, and Kitchen zones together in one action. Without this single command, the user would manually and individually link each zone. The single command may include a mouse click, a double mouse click, a button press, a gesture, or some other programmed action. Other kinds of zone scenes can be programmed.

In certain embodiments, a zone scene can be triggered based on time (e.g., an alarm clock function). For instance, a zone scene can be set to apply at 8:00 am. The system can link appropriate zones automatically, set specific music to play, and then stop the music after a defined duration. Although any particular zone can be triggered to an “On” or “Off” state based on time, for example, a zone scene enables any zone(s) linked to the scene to play a predefined audio (e.g., a favorable song, a predefined playlist) at a specific time and/or for a specific duration. If, for any reason, the scheduled music failed to be played (e.g., an empty playlist, no connection to a share, failed Universal Plug and Play (UPnP), no Internet connection for an Internet Radio station, and so on), a backup buzzer can be programmed to sound. The buzzer can include a sound file that is stored in a zone player, for example.

V. Example Ad-Hoc Network

Certain particular examples are now provided in connection with FIG. 6 to describe, for purposes of illustration, certain systems and methods to provide and facilitate connection to a playback network. FIG. 6 shows that there are three zone players 602, 604 and 606 and a controller 608 that form a network branch that is also referred to as an Ad-Hoc network 610. The network 610 may be wireless, wired, or a combination of wired and wireless. In general, an Ad-Hoc (or “spontaneous”) network is a local area network or other small network in which there is generally no one access point for all traffic. With an established Ad-Hoc network 610, the devices 602, 604, 606 and 608 can all communicate with each other in a “peer-to-peer” style of communication, for example. Furthermore, devices may join and/or leave from the network 610, and the network 610 will automatically reconfigure itself without needing the user to reconfigure the network 610. While an Ad-Hoc network is referenced in FIG. 6, it is understood that a playback network may be based on a type of network that is completely or partially different from an Ad-Hoc network.

Using the Ad-Hoc network 610, the devices 602, 604, 606, and 608 can share or exchange one or more audio sources and be dynamically grouped to play the same or different audio sources. For example, the devices 602 and 604 are grouped to playback one piece of music, and at the same time, the device 606 plays back another piece of music. In other words, the devices 602, 604, 606 and 608, as shown in FIG. 6, form a HOUSEHOLD that distributes audio and/or reproduces sound. As used herein, the term HOUSEHOLD (provided in uppercase letters to disambiguate from the user's domicile) is used to represent a collection of networked devices that are cooperating to provide an application or service. An instance of a HOUSEHOLD is identified with a household 610 (or household identifier), though a HOUSEHOLD may be identified with a different area or place.

In certain embodiments, a household identifier (HHID) is a short string or an identifier that is computer-generated to help ensure that it is unique. Accordingly, the network 610 can be characterized by a unique HHID and a unique set of configuration variables or parameters, such as channels (e.g., respective frequency bands), service set identifier (SSID) (a sequence of alphanumeric characters as a name of a wireless network), and WEP keys (wired equivalent privacy or other security keys). In certain embodiments, SSID is set to be the same as HHID.

In certain embodiments, each HOUSEHOLD includes two types of network nodes: a control point (CP) and a zone player (ZP). The control point controls an overall network setup process and sequencing, including an automatic generation of required network parameters (e.g., WEP keys). In an embodiment, the CP also provides the user with a HOUSEHOLD configuration user interface. The CP function can be provided by a computer running a CP application module, or by a handheld controller (e.g., the controller 308) also running a CP application module, for example. The zone player is any other device on the network that is placed to participate in the automatic configuration process. The ZP, as a notation used herein, includes the controller 308 or a computing device, for example. In some embodiments, the functionality, or certain parts of the functionality, in both the CP and the ZP are combined at a single node (e.g., a ZP contains a CP or vice-versa).

In certain embodiments, configuration of a HOUSEHOLD involves multiple CPs and ZPs that rendezvous and establish a known configuration such that they can use a standard networking protocol (e.g., IP over Wired or Wireless Ethernet) for communication. In an embodiment, two types of networks/protocols are employed: Ethernet 802.3 and Wireless 802.11g. Interconnections between a CP and a ZP can use either of the networks/protocols. A device in the system as a member of a HOUSEHOLD can connect to both networks simultaneously.

In an environment that has both networks in use, it is assumed that at least one device in a system is connected to both as a bridging device, thus providing bridging services between wired/wireless networks for others. The zone player 606 in FIG. 6 is shown to be connected to both networks, for example. The connectivity to the network 612 is based on Ethernet and/or Wireless, while the connectivity to other devices 602, 604 and 608 is based on Wireless and Ethernet if so desired.

It is understood, however, that in some embodiments each zone player 606, 604, 602 may access the Internet when retrieving media from the cloud (e.g., the Internet) via the bridging device. For example, zone player 602 may contain a uniform resource locator (URL) that specifies an address to a particular audio track in the cloud. Using the URL, the zone player 602 may retrieve the audio track from the cloud, and ultimately play the audio out of one or more zone players.

VI. Example System Configuration

FIG. 7 shows a system including a plurality of networks including a cloud-based network and at least one local playback network. A local playback network includes a plurality of playback devices or players, though it is understood that the playback network may contain only one playback device. In certain embodiments, each player has an ability to retrieve its content for playback. Control and content retrieval can be distributed or centralized, for example. Input can include streaming content provider input, third party application input, mobile device input, user input, and/or other playback network input into the cloud for local distribution and playback.

As illustrated by the example system 700 of FIG. 7, a plurality of content providers 720-750 can be connected to one or more local playback networks 760-770 via a cloud and/or other network 710. Using the cloud 710, a multimedia audio system 720 (e.g., Sonos™), a mobile device 730, a third party application 740, a content provider 750 and so on can provide multimedia content (requested or otherwise) to local playback networks 760, 770. Within each local playback network 760, 770, a controller 762, 772 and a playback device 764, 774 can be used to playback audio content.

VII. Example Media Experience Social Interface

As mentioned previously, embodiments for sharing a media experience among households are provided herein. The sharing of a media experience among households may allow a user to view information about a media experience of a friend in a different household, within a community, as discussed above. In one example, if the media being experienced is a musical track, the media experience information may include a title of the musical track, an album associated with the musical track, an artist associated with the musical track, a release year associated with the album, a duration associated with the musical track, and so on. If the media being experienced is a video or movie, the media experience information may include a video title, actors in the video, and a director of the video, for example. In another example, the user may share the media experience by experiencing locally a portion of the media being experienced by the friend in the different household.

FIG. 8 shows an example system configuration 800 between a media experience social interface 820 and households 850. As shown, the system configuration 800 also includes an Internet Information Service (IIS) 810 in communication with the interface 820 and in communication with the households 850. In one example, each of the households 850 may be in communication with the IIS 810 via a persistent Transmission Control Protocol (TCP) connection. In one case the persistent TCP connection is used to transmit universal plug and play (UPnP) network protocol messages between the households 850 and the IIS 810.

The IIS 810 may include a database 812 configured to be in communication with each of the households 850 to receive media experience information from, and provide data to, each respective household. The database 812 may further be configured to store and update information associated with each respective household as media experience information is received. As shown, the households 850 may include household1 842, household2 844, and household3 846, each in communication with the database 812. One or more of the household1 842, household2 844, and household3 846 may be part of a community, as described above.

Users of households 850 may form a community via invitation from a household in a community (a particular household might have started the community) or through some other defined community formation process. In some embodiments, a household may be included in multiple, different communities. In some embodiments, a community may be formed for a limited duration (e.g., an hour, a day, etc.). In other embodiments, a community exists as long as there is at least one household still part of the community. Other examples exist.

The IIS 810 may further include a household watcher 814, and a group watcher 816. The household watcher 814 may be configured to detect and retrieve updates in the database 812 associated with the households 850. As discussed before, some households may include one or more groups (or zones). Accordingly, the group watcher 816 may be configured to detect and retrieve updates in the database 812 associated with the one or more groups in any of the households 850.

The interface 820 may further include a household interface 822 and a group interface 824. In one example, the household interface 822 and group interface 824 may represent sub-regions of the interface 820. In another example, the household interface 822 and group interface 824 may represent different screens of the interface 820. As shown, the household interface 822 may be in communication with the household watcher 814 to display any updates in the database 812 detected by the household watcher 814. Similarly, the group watcher interface 822 may be in communication with the group watcher 816 to display any updates in the database 812 detected by the group watcher 816.

In one example, data displayed on the interface 820 may only include data associated with households (and associated groups) that the user using the interface 820 has access to. For example, the user may log-on to a website providing the interface 820 by providing access credentials in the form of a username and password (in some embodiments, a username and password may only be required to log-on the first time). Based on the access credentials, the IIS 810 may determine that the user has access to the community of households that includes household1 842 and household2 844. As such, the interface 820 may display, for the user to view, media information associated with household1 842 and household2 844, but not that of household3 846.

As previously described, the interface 820 may be provided on a webpage accessible via a web browser. In this case, the webpage may be implemented according to an Asynchronous JavaScript and XML (AJAX) framework, such that the interface 820 may send data to, and retrieve data from the IIS 810 asynchronously and in the background without interfering with the other information displayed on the interface 820. In other words, when an information update for a group in a household is detected, only the relevant information shown in the group interface 824 will be updated, and a refresh or reload of the webpage may not be necessary.

In one case, upon an initiation of the interface 820, data associated with households accessible by the user may be retrieved via the household watcher 814 for display on the household interface 822, and all group associated data with the same households may be retrieved via the group watcher 816 for display on the household interface 824. After initiation, the household interface 822 and group interface 824 may be updated by the household watcher 814 and group watcher 816, respectively when updates relating to the household and/or groups are detected in the database.

Example implementation of interactions between the households 850, the interface 820, and the IIS 810 may further be discussed in relation to an example flow diagram 900 of FIG. 9A. FIG. 9A shows the example flow diagram 900 for updating a media experience social interface, in accordance with at least some embodiments described herein. Method 900 shown in FIG. 9A presents an embodiment of a method that could be used in a household environment 100 with the systems 200, 202, 204, 300, 400, 500, and 800 for example, in communication with one or more devices, such as devices illustrated in FIGS. 2-5. Method 900 may include one or more operations, functions, or actions as illustrated by one or more of blocks 902-910. Although the blocks are illustrated in sequential order, these blocks may also be performed in parallel, and/or in a different order than those described herein. Also, the various blocks may be combined into fewer blocks, divided into additional blocks, and/or removed based upon the desired implementation.

In addition, for the method 900 and other processes and methods disclosed herein, the flowchart shows functionality and operation of one possible implementation of present embodiments. In this regard, each block may represent a module, a segment, or a portion of program code, which includes one or more instructions executable by a processor for implementing specific logical functions or steps in the process. The program code may be stored on any type of computer readable medium, for example, such as a storage device including a disk or hard drive. The computer readable medium may include non-transitory computer readable medium, for example, such as computer-readable media that stores data for short periods of time like register memory, processor cache and Random Access Memory (RAM). The computer readable medium may also include non-transitory media, such as secondary or persistent long term storage, like read only memory (ROM), optical or magnetic disks, compact-disc read only memory (CD-ROM), for example. The computer readable media may also be any other volatile or non-volatile storage systems. The computer readable medium may be considered a computer readable storage medium, for example, or a tangible storage device. In addition, for the method 900 and other processes and methods disclosed herein, each block in FIG. 9A may represent circuitry that is wired to perform the specific logical functions in the process.

At block 902, the method 900 may involve providing first client device data for display on a user interface. In connection to FIG. 8 and the discussions above, the user interface may be the interface 820 and the first client device data may be media experience information associated with a household or a group within a household. For instance, a first client device may be a zone player in the household or the group within the household, and the first client device data may indicate a first configuration of the zone player. In this instance, the zone player may be a zone player discussed above in connection to FIGS. 2A-2C. The first configuration of the zone player may include a playback setup (i.e. bonded zone or stereo pair involvement of the zone player) as well as current playback media content, such as a song title, an artist, and an album of a song currently being rendered in the household or group within the household by the zone player.

In one case, block 902 may involve an initiation of the interface 820 as discussed above, such that the configuration associated with the zone player may first be provided for display on the interface 820. In this case, the information provided for display may be a subset of the configuration stored on the database 812 in the IIS 810 depending on relevance, and access credentials of the user accessing the interface 820. For example, if the user is only interested in viewing information on media being experienced in the household of the friend, and not concerned with how the media is being experienced, the playback setup of the zone player in the household or group in the household may not be relevant and therefore not displayed. In another example, if the user also has access rights to the media being experienced by the friend, the user may be able to also experience the same media locally.

As indicated above, interface 820 may be provided in the form of an application on a personal device, such as an APPLE IPOD®, or a smart phone such as an APPLE IPHONE® or any ANDROID™ powered phone. In another example, the social interface may be provided on a controller of one or more media systems in a household. In yet another example, the social interface may be provided on a website on the World Wide Web and accessible over the Internet.

At block 904, the method 900 may involve accessing data in a database associated with an IIS configured to support registration and authentication of the client device with a media system. In one example, the database may be the database 812, and the IIS may be the IIS 810 of FIG. 8. In one example, the data in the database comprises device configuration data associated with the client device. As discussed above, the database 812 may be configured to store and update information associated with each respective household as media experience information is received.

At block 906, the method 900 may involve detecting a change in the device configuration data associated with the client device. As mentioned before, the IIS 810 of FIG. 8 may include the household watcher 814 and the group watcher 816. Accordingly, changes in the device configuration data associated with the client device (zone player in the household and/or group in the household) may be detected by the household watcher 814 and/or the group watcher 816.

The changes in the device configuration data in the database may result from changes in the households 850. For instance, the IIS 810 may be configured to receive data from a household, such as household1 842, if a zone player in the household1 842 begins rendering a different song, begins rendering a different playlist, stops rendering media, and so on. In response to detecting the change in household1 842, the database 812 may be updated to reflect the change.

In addition to the example changes mentioned, other example changes in the device configuration data that may be received by the database 812 and detectable by the household watcher 814 and/or group watcher 816 may include changes in the grouping of zone players in the household, changes to the names of groups or zone players in the household, changes to playlists that may be rendered in the household, or changes to accessible media by the household (modifications to the friend's media service accounts, such as RHAPSODY™, SPOTIFY™, for example). Other examples also exist.

At block 908, the method 900 may involve receiving second client device data from the IIS 810 indicative of a second configuration of the client device and reflective of the change in the device configuration data associated with the client device. Continuing with the example above, upon detection of a change in the device configuration data in the database 812, the second client device data, indicative of the updates or changes to the household1 842 may be retrieved by the household watcher 814 and/or group watcher 816.

As described above in an example, a portion of the updated device configuration data may be retrieved as the second client device data. In other words, some of the updated device configuration data may not be relevant, or accessible to the user, and may not be retrieved by the household watcher 814 and/or group watcher 816.

At block 910, the method 900 may involve providing to the user interface 820 the second client device data for display on the user interface. As with block 902, the relevant information from the database 812 of the IIS 810 may be provided. In one case, contrary to the example discussed above where only a portion of the updated device configuration data may be retrieved, all of the updated device configuration data may be retrieved by the household watcher 814 and/or group watcher 816. In this case, the user interface 820 may be configured to determine what portions of the retrieved second client device data is to be provided on the user interface 820.

FIG. 9B shows an example flow diagram 950 for providing a media experience social interface, in accordance with at least some embodiments described herein. In one example, the flow diagram 950 may represent how the first and/or second client device data are provided on the user interface 820 in blocks 902 and 910, respectively, of method 900. Method 950 shown in FIG. 9B presents an embodiment of a method that could be used in the environment 100 with the systems 200, 202, 204, 300, 400, 500, and 800 for example, in communication with one or more devices, such as devices illustrated in FIGS. 2-5. Method 950 may include one or more operations, functions, or actions as illustrated by one or more of blocks 952-956. Although the blocks are illustrated in sequential order, these blocks may also be performed in parallel, and/or in a different order than those described herein. Also, the various blocks may be combined into fewer blocks, divided into additional blocks, and/or removed based upon the desired implementation.

In addition, for the method 950 and other processes and methods disclosed herein, the flowchart shows functionality and operation of one possible implementation of present embodiments. In this regard, each block may represent a module, a segment, or a portion of program code, which includes one or more instructions executable by a processor for implementing specific logical functions or steps in the process. The program code may be stored on any type of computer readable medium, for example, such as a storage device including a disk or hard drive. The computer readable medium may include non-transitory computer readable medium, for example, such as computer-readable media that stores data for short periods of time like register memory, processor cache and Random Access Memory (RAM). The computer readable medium may also include non-transitory media, such as secondary or persistent long term storage, like read only memory (ROM), optical or magnetic disks, compact-disc read only memory (CD-ROM), for example. The computer readable media may also be any other volatile or non-volatile storage systems. The computer readable medium may be considered a computer readable storage medium, for example, or a tangible storage device. In addition, for the method 950 and other processes and methods disclosed herein, each block in FIG. 9B may represent circuitry that is wired to perform the specific logical functions in the process.

At block 952, the method 950 may involve displaying on a display screen a representation corresponding to each household of a community of households. In one example, the display screen may be associated with one of the households in the community of households. In other words, the display screen may be accessed by a user who is a member of the community. FIG. 10A shows an example first media experience social interface 1000, which may be displayed on the display screen. As suggested previously, the display screen may be that of a mobile device or personal computer screen. As shown, the interface 1000 includes a households region 1012 with household representations HOUSEHOLD 1, HOUSEHOLD 2, HOUSEHOLD 3, and HOUSEHOLD 4. In connection to the embodiments discussed previously, each of the household representations may be associated with a different household in a community. As the display screen may be associated with one of the households in the community, the household associated with the display screen providing the interface 1000 may be any one of HOUSEHOLD 1, HOUSEHOLD 2, HOUSEHOLD 3, and HOUSEHOLD 4.

In one example, one of the household representations may be selected if the user of the interface 1000 wishes to view media information associated with a household represented in the households region 1012. In one case, if HOUSEHOLD 3 is selected, the representation HOUSEHOLD 3 may be graphically distinguishable over the other household representations in the households region 1012. As shown, HOUSEHOLD 3 may be outlined and/or be in bold to indicate that HOUSEHOLD 3 has been selected. In other examples, HOUSEHOLD 3 may be graphically distinguished by being provided in a different color, different font, or different font size. Other example distinguishing features may also be possible.

As indicated above, each household shown in the households region 1012 may include one or more associated zone player groups configured to render the media in synchrony. For example, HOUSEHOLD 3 may include GROUP 1, GROUP 2, and GROUP 3. Accordingly, at block 954, the method 950 may involve displaying on the display screen a representation of a zone player group associated with a household. In one example, displaying the representation of the zone player group associated with the household may be in response to receipt of a command to select the household. As such, block 954 may involve displaying in a groups region 1008 group representations of GROUP 1, GROUP 2, and GROUP 3 representative of zone player groups associated with HOUSEHOLD 3. In this case, the display of the group representations of GROUP 1, GROUP 2, and GROUP 3 in the groups region 1008 may be in response to a selection of HOUSEHOLD 3 in the households region 1012, as suggested above.

As indicated previously, the household associated with the display screen providing the interface 1000 may be any one of HOUSEHOLD 1, HOUSEHOLD 2, HOUSEHOLD 3, or HOUSEHOLD 4. In some cases, the household associated with the display screen may not be HOUSEHOLD 3. In other words, the display screen providing the interface 1000 may be associated with a household in the community of households that is different from the household for which the representation of the zone player group and the representation of the media are displayed. In either case, one of the group representations may then be selected if the user wishes to view media information associated with a group represented in the groups region 1008. For instance, GROUP 1 may be selected, and accordingly, GROUP 1 may be graphically distinguishable over the other group representations in the groups region 1008.

Upon selection of a group, such as GROUP 1 in the groups region 1008, at block 956, the method 950 may involve displaying on the display screen a representation of media being rendered by the zone player group, GROUP 1. As shown on the interface 1000 of FIG. 10A, a representation of media being rendered by zone players in the remote zone player group, GROUP 1 may be provided in a now playing region 1010. In one case, the media representation of the media indicates information associated with the media being rendered. For example, as previously discussed, if the media being rendered is a musical track, the media experience information may include a title of the musical track, an album associated with the musical track, an artist associated with the musical track, a release year associated with the album, a duration associated with the musical track, or a record company associated with the album. In addition to the now playing region 1010 upon selection of GROUP 1, the interface 1000 may also include a display of an available media representation in a media queue region 1014. Because, as discussed before, different households, and different groups within a household may have access to different media, and/or may be capable of rendering different media, displaying available media in the media queue region 1014 may further involve determining available media to be rendered by the remote zone player group, and displaying all media accessible by zone players in the remote zone player group. In one case, if given access, the available media representation may be selectable by the user to cause the rendering of the media content by the remote zone player group.

In one example, the media queue region 1014 may provide a playlist or playback queue presently being rendered by the zone players in the group, and may therefore include media currently being rendered by the group and for which information is provided in the now playing region 1010. In this case, the now playing media may be graphically distinguishable over the other media in the available media representation 1014, as shown on the interface 1000.

While block 956 as discussed above may imply that displaying of the now playing region 1010 is upon a selection of a group representation in the groups region 1008, other embodiments may involve displaying the now playing region 1010 and media queue region 1014 upon selection of a household representation in the households region 1012. This may be the case when only one group exists within the selection household. This may also be the case if the interface is configured to select, for example, the first group representation in the groups region 1008 by default when a household is selected. In other words, in some embodiments, the selection of a group representation may be automatically made without further input from the user after the user selects a household representation. Similarly, a household representation (such as the first household representation in the households region, or the only household available) may also be configured to be automatically selected upon initiation of the interface 1000.

In addition to the households region 1012, the groups region 1008, the now playing region 1010, and the media queue region 1014, the interface 1000 may also include a controls region 1002, which may include control icons representative of available playback controls selectable to control the rendering of the media by the zone player in the remote zone player group. As previously discussed, the user of the interface 1000 may be given access to control the media experience of the friend in the household. In such a case, the available playback controls in the controls region 1002 may include icons to cause the associated remote zone players in the household to play, play next, play previous, shuffle, or repeat media in the playback queue (such as that shown in the media queue region 1014). In the case the user does not have access to control the media experience, the controls region 1002 may not be provided, or may be provided with the control icons grayed out to indicate that the control options are not available.

Also shown in FIG. 10A, the controls region 1002 of the interface 1000 may further include a playback progress bar representative of a playback progress of the media being rendered by zone players in the remote zone player group. In some examples, the playback progress bar may be selected and used to adjust the playback progress of the media being experienced at the household.

In addition to the controls region 1002, the interface 1000 may also include other controls such as a volume bar 1004 representing the volume at which the media being rendered is experienced at the household. In this case, if the user has control access to the media experience of the household or remote zone player group, the user may adjust the volume level using the volume bar 1004 to adjust the playback volume of the remote zone player group.

Further shown in FIG. 10A is a search box 1006 on the interface 1000. In one example, as shown, the search box 1006 may be used to find by text or drop down selection a specific household in the community. In other examples, the search box 1006 may be used to find specific media, or groups within a specific household, or a community.

In one example, to further enhance the experience of the user wishing to view information on media being experienced by another household, additional information may be provided on the interface 1000. FIG. 10B shows an example second media experience social interface 1050. As shown, the interface 1050 may include a households region 1062, a groups region 1058, a now playing region 1060, and a media queue region 1064, similar to the households region 1012, groups region 1008, now playing region 1010, and media queue region 1014, respectively, of the interface 1000 of FIG. 10A. In addition to the interface 1000, the interface 1050 may include a lyrics region 1006 displaying a textual representation of lyrics associated with the media being rendered, if the media is a musical track. The interface 1050 may also include a photos region 1068 showing images associated with an artist of the musical track. Other information may also be provided on the interface 1050, such as a biography of the artist, or interesting facts about the musical track or album. Other examples are also possible.

In further embodiments of the present application that may not be explicitly shown in FIG. 10A or 10B, a representation of each zone player in a zone player group may be provided on the display screen in response to a selection of the zone player group. For instance, if GROUP 1 includes two zone players rendering media as a studio pair, selection of GROUP 1 may result in providing on the display screen representations of a left zone player and a right zone player of GROUP 1. In such embodiments, modifications of groupings of zone players within a household, or zone player groups within the household may further be made in response to receiving commands from a user indicating such modifications. In one example, the left and right zone players may be modified to each play both left and right channels of the media content. In another example, one of the zone players may be removed from GROUP 1 and added to GROUP 2. In a yet another example, one or more zone players from GROUP 2 may be added to GROUP 1. As with other means of controlling the media experience of a remote household, the ability to modify the groupings of zone players via the interface 1000 or 1050 may depend on the access rights given to the user of the interface 1000 or 1050.

As discussed in an example above, a friend may give the user control access to the media experience at the household or group. This may be in addition to the friend giving the user any access at all to the media experience at the household or group. For instance, the present application may allow sharing of media experience information between households only to the extent that an owner of a household or group allows. In other words, media experience sharing rights may be determined by the owner of the household or group.

FIG. 11 shows an example interface 1100 for configuring a media experience sharing configuration. The interface 1100 may also be used to join a community and set up parameters. In one example, the interface 1100 may be used by a user of a first household to determine what level of access a user of second household in the community may have to the first household's media experience.

As shown, the interface 1100 may include a household name box 1102, a group selection box 1104, sharing options 1106, and sharing scope 1108. The household name box 1102 may display an editable name of a household representative of the household on the network interface. As such, one may edit the name of the household to be displayed to others. The group selection box 1104 may then provide the user of the first household a selection of groups in the first household. In one example, a selection of a group in the first household may allow the user to edit a name of the selected group. In another example, the selection of the group may show the sharing options 1106 and sharing scope 1108 associated with the selected group.

As shown, the sharing options 1106 of the group may include example types of media experience sharing such as allowing the network interface to view media being rendered by one or more zone player groups in the first household, view all media accessible by one or more zone player groups in the first household, control rendering of the media being rendered by one or more zone player groups in the first household, or view media in a playlist being rendered by one or more zone player groups in the first household. Also as shown, the sharing scope 1108 may include example scope of sharing such as allowing access to the one or more zone player groups in the first household via the network interface by nobody, everyone in communication with the first household, or users associated with other households in a community of households including the first household.

As such, a sharing scope may correspond to a sharing option. For instance, as shown, the sharing scope of “nobody” has been selected for the sharing option of “control my queue.” Accordingly, no one (outside of the first household) has the access rights to control the queue of the selected group shown in the group selection box 1104 for the household. In another example, as shown, the sharing scope of “everybody” has been selected for the sharing option of “see what I'm listening to.” Accordingly, anyone with access to the social interface, and in communication with the first household via a community may view what is being rendered by the selected group in the household. Other examples are also possible. For instance, interface 1100 may also enable the user of the first household to select a community from a plurality of communities, if the user is a member of multiple communities. As such, different sharing options and sharing scope may be set for each community.

In addition to allowing a user of the first household to view the sharing configurations, the interface 1100 of FIG. 11 may also allow the user to modify the sharing configurations. For example, the user may select a different sharing scope in the sharing scopes 1108 for a different sharing option in the sharing options 1106. In such a case, the interface 1100 may further include a selectable icon, such as a submit button to apply the changes in sharing configurations to the selected group in the household. In another case, any selection of a sharing scope or sharing option may automatically be applied to the selected group in the household.

In another example, the user may select a corresponding sharing scope for each sharing option before selecting a group via the group selection box 1104. In such a case, the interface 1100 may be configured to apply the selected sharing configuration to the selected group rather than simply displaying the sharing configurations of the selected group, as indicated above. Other example implementations of the interface 1100 may also be possible.

VIII. Conclusion

The present application discloses various example systems, methods, apparatus, and articles of manufacture including, among other components, firmware and/or software executed on hardware. However, such examples are merely illustrative and should not be considered as limiting. For example, it is contemplated that any or all of these firmware, hardware, and/or software components can be embodied exclusively in hardware, exclusively in software, exclusively in firmware, or in any combination of hardware, software, and/or firmware. Accordingly, while the following describes example systems, methods, apparatus, and/or articles of manufacture, the examples provided are not the only way(s) to implement such systems, methods, apparatus, and/or articles of manufacture.

As provided in the embodiments discussed above, the present application provides a social interface for sharing media experience information between households. In one aspect, a method for displaying media information for a household of a community of households on a display screen is provided. The method involves displaying on a display screen a representation of a zone player group associated with a household responsive to receipt of a command to select the household from a community of households, and displaying on the display screen a representation of media being rendered by the zone player group, wherein the representation of the media indicates information associated with the media being rendered.

In another aspect, a non-transitory computer readable medium is provided. The non-transitory computer readable medium has stored thereon instructions executable by a computing device to cause the computing device to perform functions. The functions include displaying on a display screen a representation of a zone player group associated with a household responsive to receipt of a command to select the household from a community of households, and displaying on the display screen a representation of media being rendered by the zone player group, wherein the representation of the media indicates information associated with the media being rendered.

Additionally, references herein to “embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one example embodiment of the invention. The appearances of this phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. As such, the embodiments described herein, explicitly and implicitly understood by one skilled in the art, can be combined with other embodiments.

The specification is presented largely in terms of illustrative environments, systems, procedures, steps, logic blocks, processing, and other symbolic representations that directly or indirectly resemble the operations of data processing devices coupled to networks. These process descriptions and representations are typically used by those skilled in the art to most effectively convey the substance of their work to others skilled in the art. Numerous specific details are set forth to provide a thorough understanding of the present disclosure. However, it is understood to those skilled in the art that certain embodiments of the present disclosure can be practiced without certain, specific details. In other instances, well known methods, procedures, components, and circuitry have not been described in detail to avoid unnecessarily obscuring aspects of the embodiments. Accordingly, the scope of the present disclosure is defined by the appended claims rather than the forgoing description of embodiments.

When any of the appended claims are read to cover a purely software and/or firmware implementation, at least one of the elements in at least one example is hereby expressly defined to include a tangible medium such as a memory, DVD, CD, Blu-ray, and so on, storing the software and/or firmware. 

The invention claimed is:
 1. A method to be performed by a computing system, the method comprising: causing, via a network interface, display of a household management interface for multiple media playback systems that comprise one or more respective playback devices, wherein a first control interface of the household management interface comprises (i) respective representations of the multiple media playback systems and (ii) first status information comprising indications of one or more respective first statuses corresponding to each media playback system of the multiple media playback systems; receiving, via a households control of the household management interface, input data representing a selection of a particular media playback system from among the multiple media playback systems, wherein the household management interface is switchable among a plurality of second control interfaces corresponding to each media playback system of the multiple media playback systems via the households control; based on receiving the input data representing the selection of the particular media playback system, causing, via the network interface, display of a particular second control interface of the household management interface, the second control interface comprising (i) playback controls to control playback on playback devices of the particular media playback system and (ii) second status information comprising indications of two or more second statuses corresponding to respective parameters of the particular media playback system; receiving, via the network interface, data representing updated status information for at least one media playback system of the multiple media playback systems; and based on receiving the data representing updated status information for at least one media playback system, updating the household management interface to display the updated status information for at least one media playback system of the multiple media playback systems.
 2. The method of claim 1, wherein causing display of the household management interface for multiple media playback systems comprises causing display of the household management interface in a web browser on a computing device.
 3. The method of claim 1, wherein causing display of the household management interface for multiple media playback systems comprises causing display of the household management interface in a media playback system application on a mobile device.
 4. The method of claim 1, wherein the one or more first statuses corresponding to each media playback system of the multiple media playback systems comprise respective names of the multiple media playback systems, and wherein the household management interface comprises a household name control selectable to edit the respective names of the multiple media playback systems.
 5. The method of claim 1, wherein the two or more second statuses corresponding to respective parameters of the particular media playback system comprise (i) one or more playback statuses corresponding to respective groups of one or more playback devices in the particular media playback system and (ii) respective names of the groups of one or more playback devices in the particular media playback system.
 6. The method of claim 1, wherein the one or more first statuses corresponding to each media playback system of the multiple media playback systems comprise respective metadata indicating audio content currently playing on the corresponding media playback system of the multiple media playback systems.
 7. The method of claim 1, further comprising: receiving, via a settings control of the household management interface, input data representing particular values of one or more settings; and applying the particular values of the one or more settings to two or more media playback systems of the multiple media playback systems.
 8. The method of claim 7, wherein the one or more settings comprise a sharing setting.
 9. The method of claim 1, further comprising: applying values of the one or more settings of a first media playback system of the multiple media playback systems to a second media playback system of the multiple media playback systems.
 10. The method of claim 1, further comprising: receiving input data indicating a request to add an additional media playback system to the multiple media playback systems; and based on receiving the input data, updating the household management interface to include the additional media playback system in the multiple media playback systems.
 11. Tangible, non-transitory computer-readable media having stored thereon instructions that, when executed by one or more processors of a computing device, cause the computing device to perform functions comprising: causing display of a household management interface for multiple media playback systems that comprise one or more respective playback devices, wherein a first control interface of the household management interface comprises (i) respective representations of the multiple media playback systems and (ii) first status information comprising indications of one or more respective first statuses corresponding to each media playback system of the multiple media playback systems; receiving, via a households control of the household management interface, input data representing a selection of a particular media playback system from among the multiple media playback systems, wherein the household management interface is switchable among a plurality of second control interfaces corresponding to each media playback system of the multiple media playback systems via the households control; based on receiving the input data representing the selection of the particular media playback system, causing, via a network interface, display of a particular second control interface of the household management interface, the second control interface comprising (i) playback controls to control playback on playback devices of the particular media playback system and (ii) second status information comprising indications of two or more second statuses corresponding to respective parameters of the particular media playback system; receiving, via the network interface, data representing updated status information for at least one media playback system of the multiple media playback systems; and based on receiving the data representing updated status information for at least one media playback system, updating the household management interface to display the updated status information for at least one media playback system of the multiple media playback systems.
 12. The tangible, non-transitory computer-readable media of claim 11, wherein causing display of the household management interface for multiple media playback systems comprises causing display of the household management interface in a web browser on the computing device.
 13. The tangible, non-transitory computer-readable media of claim 11, wherein causing display of the household management interface for multiple media playback systems comprises causing display of the household management interface in a media playback system application on the computing device.
 14. The tangible, non-transitory computer-readable media of claim 11, wherein the one or more first statuses corresponding to each media playback system of the multiple media playback systems comprise respective names of the multiple media playback systems, and wherein the household management interface comprises a household name control selectable to edit the respective names of the multiple media playback systems.
 15. The tangible, non-transitory computer-readable media of claim 11, wherein the two or more second statuses corresponding to respective parameters of the particular media playback system comprise (i) one or more playback statuses corresponding to respective groups of one or more playback devices in the particular media playback system and (ii) respective names of the groups of one or more playback devices in the particular media playback system.
 16. The tangible, non-transitory computer-readable media of claim 11, wherein the one or more first statuses corresponding to each media playback system of the multiple media playback systems comprise respective metadata indicating audio content currently playing on the corresponding media playback system of the multiple media playback systems.
 17. The tangible, non-transitory computer-readable media of claim 11, wherein the functions further comprise: receiving, via a settings control of the household management interface, input data representing particular values of one or more settings; and applying the particular values of the one or more settings to two or more media playback systems of the multiple media playback systems.
 18. The tangible, non-transitory computer-readable media of claim 17, wherein the one or more settings comprise a sharing setting.
 19. The tangible, non-transitory computer-readable media of claim 11, wherein the functions further comprise: applying values of the one or more settings of a first media playback system of the multiple media playback systems to a second media playback system of the multiple media playback systems.
 20. The tangible, non-transitory computer-readable media of claim 11, wherein the functions further comprise: receiving input data indicating a request to add an additional media playback system to the multiple media playback systems; and based on receiving the input data, updating the household management interface to include the additional media playback system in the multiple media playback systems. 